home *** CD-ROM | disk | FTP | other *** search
Text File | 1991-03-06 | 1.5 KB | 46 lines | [TEXT/GEOL] |
- Item 0233256 12-Oct-90 12:27PDT
-
- From: PHAROS.TECH Pharos Tech, Tech Staff,PRT
-
- To: MACAPP.TECH$ MacApp Technical
-
- Sub: RE: MacApp 2.0b5 vs MPW 3.1?
-
- From: Schmitz, Scott D. on Fri, Oct 12, 1990 3:28 PM
- Subject: RE: MacApp 2.0b5 vs MPW 3.1?
- To: MacApp
-
- It's like this.
-
- Earlier versions of MacApp (Pre 2.0 final) used an earlier version of the
- Pascal compiler (Pre 3.1). The current version of the Pascal compiler does
- some extra syntax checking. One of the things it checks for is unsafe handle
- usage. Due to the new Pascal compiler the MacApp team found and fixed a few
- problems. You have a version of MacApp which is before those fixes were made.
-
- I would recommend that you get the 2.0 final version of MacApp.
-
- The problem that you encountered occurrs typically when you pass in an object
- variable which is greater than 4 bytes as a paramater into a procedure. For
- example:
-
- StrConcat(fView.Name);
-
- would blow chunks if Name was a Str255 and fView was an object reference.
-
- To get around this, use a temporary variable.
-
- For example:
-
- SillyStr := fView.Name;
- StrConcat(SillyStr);
- fView.Name := SillyStr; { Only needed if StrCat passed SillyStr in as a VAR}
-
- The problem occurrs because objects are really handles and the Pascal compiler
- dereferences the handle when you pass in a variable of larger than 4 bytes into
- a procedure or pass in a variable of any size as a VAR paramater.
-
- Scott.
-
-
-